Add Name field to Namespace class definition#52
Open
evan-aveva wants to merge 2 commits into
Open
Conversation
evan-aveva
requested review from
BharathIndukuri and
jakestickaaveva
and removed request for
BharathIndukuri and
jakestickaaveva
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Related information or background
The name field is returned by the Namespaces API, but is not included in the Namespace class definition. This prevents accessing the Namespace name without extending the library.
Checklist
Versioning
README.mdis incrementedHISTORY.mdis incrementedsetup.pyis incremented